Skip to content

Do not cache :spring-boot-project:spring-boot-docs:asciidoctor* tasks #34199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

jprinet
Copy link
Contributor

@jprinet jprinet commented Feb 15, 2023

Goal here is to document the cache misses on those 3 tasks:

  • :spring-boot-project:spring-boot-docs:asciidoctor
  • :spring-boot-project:spring-boot-docs:asciidoctorMultipage
  • :spring-boot-project:spring-boot-docs:asciidoctorPdf

the 3 task inputs runRemoteSpringApplicationExample, runSpringApplicationExample, runLoggingFormatExample are log files containing timestamps, pid and absolute path, for example:

2023-02-14T15:54:42.600+01:00 INFO 61537 --- [ main] o.s.b.devtools.RemoteSpringApplication : Starting RemoteSpringApplication v3.1.0-SNAPSHOT using Java 17.0.1 with PID 61537 (/Users/myuser/.m2/repository/org/springframework/boot/spring-boot-devtools/3.1.0-SNAPSHOT/spring-boot-devtools-3.1.0-SNAPSHOT.jar started by myuser in /opt/apps/)

We could consider changing the log pattern with logging.pattern.console to day precision and disable logging on o.s.b.devtools to get a cache hit, but I assume that those outputs are part of the documentation and you want the default format / output to be displayed.
In my experience the cost of having those re-running was significant: 2m 31.896s of CPU time.

This is the outcome with the cache miss documented in Gradle Enterprise:
Screenshot 2023-02-15 at 8 48 54 AM

In addition to that, naming the inputs make the troubleshooting easier in Gradle Enterprise, this is what you can get instead of anonymous $1, $2, $3:
Screenshot 2023-02-15 at 8 49 13 AM

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 15, 2023
@wilkinsona wilkinsona added type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged labels Feb 15, 2023
@wilkinsona wilkinsona added this to the 2.7.x milestone Feb 15, 2023
@wilkinsona wilkinsona modified the milestones: 2.7.x, 2.7.9 Feb 15, 2023
@wilkinsona
Copy link
Member

Thanks very much, @jprinet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants